Skip to content

[Docs] Increase vm.max_map_count suggested value (attempt 2)#9004

Closed
shainaraskas wants to merge 9 commits intoelastic:2.16from
shainaraskas:216-vm-mmc-attempt-2
Closed

[Docs] Increase vm.max_map_count suggested value (attempt 2)#9004
shainaraskas wants to merge 9 commits intoelastic:2.16from
shainaraskas:216-vm-mmc-attempt-2

Conversation

@shainaraskas
Copy link
Copy Markdown
Member

We want to recommend a higher vm.max_map_count for Elasticsearch environments - additional context in issue

Changes made:

  • bumped the recommended max_map_count from 262144 to 1048576 in docs and examples, with the exception of GKE Autopilot
  • Documented GKE Autopilot exception in recommendations
  • bumped NOTICE.txt to satisfy CI

recreation of #8971 (couldn't be merged because it wasn't from a fork)

What issues does this PR fix?
Part of https://github.com/elastic/docs-content-internal/issues/592

@prodsecmachine
Copy link
Copy Markdown
Collaborator

prodsecmachine commented Jan 8, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@barkbay barkbay added the >docs Documentation label Jan 15, 2026
@botelastic botelastic Bot removed the triage label Jan 15, 2026
@botelastic botelastic Bot removed the triage label Jan 15, 2026
Copy link
Copy Markdown
Contributor

@barkbay barkbay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

The kernel setting `vm.max_map_count=262144` can be set on the host directly, by a dedicated init container which must be privileged, or a dedicated Daemonset.
The kernel setting `vm.max_map_count=1048576` can be set on the host directly, by a dedicated init container which must be privileged, or a dedicated Daemonset.

IMPORTANT: For {{es}} version 8.16 and later, set the `vm.max_map_count` kernel setting to `1048576`; for {{es}} version 8.15 and earlier, set `vm.max_map_count` to `262144`. The exception is in GKE Autopilot environments, where `vm.max_map_count` must always be set to `262144`. This is because any privileged DaemonSet in GKE Autopilot must match the DaemonSet pre-approved by Google.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand that this is a backport to 2.16, I was wondering if we still want to mention the ComputeClass in the "current" documentation:

Suggested change
IMPORTANT: For {{es}} version 8.16 and later, set the `vm.max_map_count` kernel setting to `1048576`; for {{es}} version 8.15 and earlier, set `vm.max_map_count` to `262144`. The exception is in GKE Autopilot environments, where `vm.max_map_count` must always be set to `262144`. This is because any privileged DaemonSet in GKE Autopilot must match the DaemonSet pre-approved by Google.
IMPORTANT: For {{es}} version 8.16 and later, set the `vm.max_map_count` kernel setting to `1048576`; for {{es}} version 8.15 and earlier, set `vm.max_map_count` to `262144`. The exception is in GKE Autopilot environments, where `vm.max_map_count` must always be set to `262144` when using a DaemonSet instead of a [ComputeClass](/deploy-manage/deploy/cloud-on-k8s/virtual-memory.md#k8s_using_a_computeclass_to_set_virtual_memory). This is because any privileged DaemonSet in GKE Autopilot must match the DaemonSet pre-approved by Google.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that content is covered over here: elastic/docs-content#4490

sorry for the noise - this PR was me trying to troubleshoot why I was blocked from merging :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>docs Documentation v2.16.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants